View file protection snapshot policies
Network-attached storage is a file-level storage architecture that makes stored data more accessible to networked devices.
About this task
See Understanding PowerMax File for storage systems for an overview of PowerMax File.
A snapshot schedule manages the life cycle of file system snapshots. A schedule is created at the NAS server level and is assigned to one or more file systems within the NAS server. A schedule follows a rule that decides when a snapshot is taken place and when a snapshot is expired based on retention policy. As shown in Figure 1, Schedule rules are persisted in nameDB on cluster VDM. A schedule is persisted in nameDB on the user VDM. By default, a schedule is replicated and stored within configFS on user VDM. For the cases of local snapshot, a schedule can be configured as non-replicated and is stored within rootFS on user VDM.
Snapshots are not replicated on the destination. Only the snap schedules are replicated. However, user can take a snapshot or attach snap schedule on the destination.
If system Write pending WP% is above 50%, system gives priority to the IOs. Once WP% ratio comes down to below 50%, SRDF sync resumes.
If there are large numbers of invalid tracks that must be synchronized between the source and destination, the start operation might report a failure to the UI (Unisphere for PowerMax) but it completes in the background. Once the SRDF state moves into synchronized or consistent state which is reported in the replication session page, re-run the start operation from the UI.
Auto failover if there is disaster is not supported. The user has to perform failover of the replication sessions manually.
Click
in the upper right corner to see a
Initial Configuration
window that outlines the configuration sequence. An overview of this configuration sequence is provided in
Understanding PowerMax File for storage systems.
